Change summary

This PR adds support for a --no-default-domain flag for the Compute Deploy & Publish commands, allowing users to opt out of the automatic allocation of a domain when one isn't specified.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

• Does your submission pass tests?

 TEST_COMPUTE_DEPLOY=1 go test -v ./pkg/commands/compute -run "TestDeploy/success_with_--no-default-domain_flag_for_new_service"
 ...
 --- PASS: TestDeploy (0.70s)
    --- PASS: TestDeploy/success_with_--no-default-domain_flag_for_new_service (0.68s)
    
TEST_COMPUTE_DEPLOY=1 go test -v ./pkg/commands/compute -run "TestDeploy/success with --no-default-domain but explicit --domain provided"
...
--- PASS: TestDeploy (0.10s)
    --- PASS: TestDeploy/success_with_--no-default-domain_but_explicit_--domain_provided (0.08s)    

Changes to Core Features:

• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

User Impact

Users can now opt out of the automatic allocation of a domain when one isn't specified when deploying a new Compute service.

Additional Notes

Local testing confirms this new flag is working as expected.